Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-204548 | RHEL-07-030690 | SV-204548r603261_rule | Medium |
Description |
---|
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. When a user logs on, the auid is set to the uid of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215 |
STIG | Date |
---|---|
Red Hat Enterprise Linux 7 Security Technical Implementation Guide | 2021-12-02 |
Check Text ( C-4672r462642_chk ) |
---|
Verify the operating system generates audit records when successful/unsuccessful attempts to use the "sudo" command occur. Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": # grep -iw /usr/bin/sudo /etc/audit/audit.rules -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=unset -k privileged-priv_change If the command does not return any output, this is a finding. |
Fix Text (F-4672r462643_fix) |
---|
Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "sudo" command occur. Add or update the following rule in "/etc/audit/rules.d/audit.rules": -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=unset -k privileged-priv_change The audit daemon must be restarted for the changes to take effect. |